it was intentionally done as own method, as too-fd capture is vastly more difficult than too-sys capture
as it practically needs tee fds to be set up/consumed

as the implementation will vastly differ and cant share logic, using a flag instead of a new implementation name seemed misleading

@RonnyPfannschmidt
This is an implementation "detail" that does not mean we should not "split --capture on parens", does it?

I guess with regard to capteesys this is (or should be) similar to using capsys fixture + -s.

for the capture fixture, it seems like it would be helpful if it could be turned into one fixture that may be configured by a parameter/marker instead of having many mutually exclusive fixtures

side-note, the more tricky implementation that's necessary for a tee-fd is potentially also a gateway to a pty/tee-pty capture backed

side-note, the more tricky implementation that's necessary for a tee-fd is potentially also a gateway to a pty/tee-pty capture backed

Yes.
You need a thread (or multiple), and also master, slave = pty.openpty() when handling stdin (IIRC), otherwise os.pipe() is fine for stdout/stderr.

for the capture fixture, it seems like it would be helpful if it could be turned into one fixture that may be configured by a parameter/marker instead of having many mutually exclusive fixtures

That should be the long-term goal, given that there is the tee option now and dup/merge maybe later.
Let's not worry about adding this one (capteesys) as a fixture here then.

good point

Removing "[WIP]".
I think it makes sense to have this for #6690 (review).

@blueyed are you planning to merge it soon? It would be useful to have it before I'll resume work on #6690. Maybe you need some help?

@aklajnert it's not really clear to me how to proceed here (#6671 (comment)).
Please fee free to either rebase #6690 on this one, and/or include what you find useful from here, but likely better as separate/base commits then.

@aklajnert I've pulled out #6765, without the generalisation of _getcapure.

Closing for now, can be revisited later, or pulled into #6690 then.

FWIW _getcapture should be named _get_multicapture, and could be on the module - or a classmethod MultiCapture.from_method, which might be preferred. (=> #6788)